feat(release): build binaries for 4 targets on tag push#80
Merged
Conversation
Closes #58. The release workflow had a TODO-shaped build job that didn't actually produce any artifact, and the release job had no `files:` attached. Tags would create a Release with notes but no binaries; users had to `cargo install --path .` from source. Wire it up: - **build** job becomes a matrix across four targets: * `x86_64-unknown-linux-gnu` on ubuntu-latest (native) * `aarch64-unknown-linux-gnu` on ubuntu-latest via `cross` * `aarch64-apple-darwin` on macos-latest (native) * `x86_64-pc-windows-msvc` on windows-latest (native, `.exe`) - Each lane runs `cargo build --release --target <T>`, stages the binary + LICENSE + README.adoc into a versioned directory, and packages it as `.tar.gz` (Unix) or `.zip` (Windows) with a sidecar `.sha256` checksum. - Artifacts upload per-target with `actions/upload-artifact`. - **release** job now downloads all `release-*` artifacts and attaches `*.tar.gz`, `*.zip`, and `*.sha256` to the GitHub Release via `softprops/action-gh-release`. The SLSA provenance job's `base64-subjects` still needs wiring (out of scope for this issue); the build artifacts are already SHA-256 checksummed via the sidecar files. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Per V-L3-L1: the release workflow had TODO-shaped stubs. Tags would create a Release with notes but no binaries; users had to
cargo install --path ..Wire it up:
x86_64-unknown-linux-gnu(ubuntu-latest, native)aarch64-unknown-linux-gnu(ubuntu-latest, viacross)aarch64-apple-darwin(macos-latest, native)x86_64-pc-windows-msvc(windows-latest, native,.exe).tar.gzor.zipwith a sidecar.sha256.release-*artifacts and attaches them viasoftprops/action-gh-release.Permissions unchanged at top level (
contents: read); release job hascontents: write(already needed). All actions SHA-pinned. SLSA provenancebase64-subjectswiring is out of scope.Closes
Test plan
v0.1.0-rc1tag after merge to verify four artifacts upload to the Release